Update syntax image examples to use images path
#1162
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As a convention our images are stored in a `images` directories, but our syntax instructions use `img` in the example image paths. This caused confusion for one developer so far, so I think it's worth updating our guide.
kilfoyle
added
bug
documentation
Contributor
colleenmcginnis
left a comment
colleenmcginnis
left a comment
There was a problem hiding this comment.
@kilfoyle I think you'll also need to rename the docs/syntax/img directory to docs/syntax/images and then update any other references to images outside this Markdown file to also point to images instead of img.
Contributor
Author
|
Thanks @colleenmcginnis! I renamed |
Mpdreamz
approved these changes
May 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As a convention our images are stored in directories named
images, but our syntax instructions useimgin the example image paths. This caused confusion for one developer so far, so I think it's worth updating our guide.